Skip to main content

Week 4

Dec 12/19/2022​

  1. Upload debug screenshots for the Django.
  2. Plots for timeseries from the INP files.
  3. Reply to the Azure support people for the ORSANCO issue.
  4. Reply Brian on Collimator. Check the output.
    1. Still the same error. Not sure what is going wrong. I have replied back. Brian is looking into it.
  5. TDEngine controller → waiting on reply from Ragu.

Long term tasks​

  1. Caching and quicker builds in other repos using GitHub actions
    1. Remaining for a few repos.
  2. Adding notebooks into version control for nbdev
  3. Docs migration action plan
  4. AI related tasks
    1. multi-variate multi-step timeseries forecasting
    2. check forums for replies on clipping in forecasting.
    3. Pipe breaks streamlit app → check status and migration of remaining algorithms
    4. Documentation of CCTV processes
    5. Next steps on all our AI tasks and their current state
  5. Doc on Azure Blob storage for video/image files
  6. Deploying of streamlit app
    1. Refer doc HERE
  7. Papers to write (word documents for all 3 were started)
    1. Paper 1: Multi label segmentation
    2. Paper 2: Complexity of vehicle detection with traffic cam images
    3. Paper 3: Complexity of flood detection

Meeting with Ragu (12/19/2022)​

  1. Have key-vault for DB params
  2. When the GH action gets fired
    1. Connect to key-vault
    2. Grant access through managed identity

App services are deployed in a multi tenant environment

note

TDEngine has no ORM.

Docs migration plan​

  1. Only keep projects being done by the interns on the People site.
  2. Move all the other projects to the docs site.
caution

Projects on the people site contain the latest version of the project docs.

Steps involved​

  1. Copy the contents: projects directory on the People repo → project directory on the docs repo.
  2. Compare and push the changes on the docs repo
  3. Remove all GQC related confidential stuff from the people repo.
  4. (Probably delete git history -- might need to consult with Jake)
  5. Push the changes.

Dec 12/20/2022​

  1. ORSANCO (Clean install steps)
    1. List all existing resources related to ORSANCO
    2. After listing all of them, delete all of them taking careful notes
    3. From orsanco_frontend, riverflows_django and orsanco-flows VM, delete the workflow files and push the changes.
    4. While creating the resources again, make sure that they are in the same region. (something like US Central or US East 2, etc)
    5. For the frontend, create new SWA
    6. For the riverflows_django, create a new app service, update CORS origins and the DB params on the Azure configuration through the Azure Portal.
    7. For the VM, ask for Jake's notes for the DB and VM config and then restore the dump

Steps taken​

  1. Ruling out the possibility that since resources are not in the same region, they're not able to communicate with each other.
  2. Only the SWA (salmon-mud) and the DRF (Django Rest Framework) (riverflows.azurewebsites.net) were in Central US, rest all the resources were in the East US 2.
  3. Hence, new SWA and DRF were created in the East US 2 region.
  4. Doing so, did not solve the problem, hence this approach was bagged.

Running Django through the VM​

This tutorial was followed for running Django on Ubuntu Server 20.04 LINK

danger

While running the Django app on the VM, CORS headers get handled by NGINX, not Django.

  • Appropriate settings were made in NGINX
  • We were able to successfully run the frontend locally, connecting to Django on the VM and getting the data from the PostgreSQL database.

Current status of ORSANCO​

  1. The VM is served on HTTP.
  2. The SWA is served on HTTPS.
  3. You can retreive unsecure data on a secure channel, hence you get a mixed content error.
  4. A support issue with Microsoft has been opened. Waiting on its reply.

Collimator​

  1. Brian replied saying that the issue is fixed, upon a quick test. tsai imports are working and even the model loading is working.

Dec 12/21/2022​

  1. Get the DNS working for the VM.
  2. static files for Django on the VM.
  3. A new self signed certificate was created
  4. Certificate was put on the VM
  5. NGINX was configured the new SSL certificate
  6. The website is running properly on everyone's system
  7. Need some clarification from Azure support to get a trusted certificate
  8. Waiting on reply from the Azure guy
  9. Revised doc for AI+IoT hackathon

Adding SSL/TLS certificates for Apache and NGINX on Azure Virtual Machines

Dec 12/22/2022​

  1. ORSANCO
    1. ORSANCO React front-end: Steps to get around SSL and testing it on the phone.
  2. Document for the AI3 Hackathon is ready.

Dec 12/23/2022​

  1. review python doc from Jake
  2. reply to Jake's comments on the AI3 competition doc
  3. add doc for python dev standards on docs post review
  4. add doc for additional React materials
  5. doc for starting the ORSANCO website. LINK
Last updated on by Deven